Methods and systems for automatically locating a provisioning server

ABSTRACT

A provisioning client can be configured to automatically locate a provisioning server in a provisioning environment in order to perform software provisioning. The provisioning client can locate the provisioning server by detecting the location of the provisioning server or by selecting the appropriate provisioning server from a record of available provisioning servers. Once located, the provisioning client can be configured to establish a connection with the provisioning server and to request or receive software provisioning.

FIELD

This invention relates generally to software provisioning.

DESCRIPTION OF THE RELATED ART

Software provisioning is the process of selecting a target machine, such as a server, loading the appropriate software (operating system, device drivers, middleware, and applications), and customizing and configuring the system and the software to make it ready for operation. Software provisioning can entail a variety of tasks, such as creating or changing a boot image, specifying parameters, e.g. IP address, IP gateway, to find associated network and storage resources, and then starting the machine and its newly-loaded software. Typically, a system administrator will perform these tasks using various tools because of the complexity of these tasks. Unfortunately, there is a lack of provisioning control tools that can adequately integrate and automate these tasks.

Typically, software provisioning involves a provisioning client program interacting with a provisioning server. The provisioning client assists with the provisioning of the software from the provisioning server to the target machines. To facilitate this interaction, the provisioning client must be supplied with the identity, such as network ID, and location, such as a network address, of the provisioning server with which to communicate. Typically, this involves a user manually entering the identity and location of the appropriate provisioning server. As such, the user must identify and locate the appropriate provisioning server and must have knowledge of how to enter the specifics of the provisioning server in the provisioning client.

This becomes cumbersome as provisioning clients are often spread across wide geographic locations and may need to access different provisioning server. Because provisioning clients may access different provisioning servers, the provisioning clients cannot easily be associated with a predefined provisioning server. Additionally, because the provisioning servers may change over time due to network or service changes, the provisioning clients cannot be preprogrammed with the identify and location of a specific provisioning server. Accordingly, it would be desirable to provide a provisioning environment in which a provisioning client can automatically locate provisioning servers.

BRIEF DESCRIPTION OF THE DRAWINGS

Various features of the embodiments can be more fully appreciated, as the same become better understood with reference to the following detailed description of the embodiments when considered in connection with the accompanying figures, in which:

FIG. 1 illustrates an overall provisioning environment in which various embodiments of the present teachings can be practiced;

FIG. 2 illustrates the overall provisioning environment in which a provisioning client can automatically locate a provisioning server, according to various embodiments;

FIG. 3 illustrates an exemplary hardware configuration for a provisioning server, according to various embodiments; and

FIG. 4 illustrates a flowchart for locating provisioning servers, according to various embodiments.

DETAILED DESCRIPTION OF EMBODIMENTS

For simplicity and illustrative purposes, the principles of the present invention are described by referring mainly to exemplary embodiments thereof. However, one of ordinary skill in the art would readily recognize that the same principles are equally applicable to, and can be implemented in, all types of information and systems, and that any such variations do not depart from the true spirit and scope of the present invention. Moreover, in the following detailed description, references are made to the accompanying figures, which illustrate specific embodiments. Electrical, mechanical, logical and structural changes may be made to the embodiments without departing from the spirit and scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense and the scope of the present invention is defined by the appended claims and their equivalents.

Embodiments of the present teachings relate to systems and methods for automatically locating a provisioning server in a software provisioning environment. More particularly, a provisioning client can be configured to automatically locate a provisioning server in order to request software provisioning.

According to embodiments, a provisioning client can be configured to include a locater module. The locater module can be configured to automatically locate a provisioning server in the provisioning environment in order to perform software provisioning. Once located, the provisioning client can be configured to establish a connection with the provisioning server and to request software provisioning.

In embodiments, in order to locate the provisioning server, the provisioning client can be configured to detect broadcast network information from the provisioning server in order establish a connection with the provisioning server. In particular, a provisioning server can be configured to broadcast its network information, such as network identification, network location, or configuration. In order establish a connection, the locater module of the provisioning client be configured to automatically detect the broadcast network information from the provisioning server. Once detected, the provisioning client can establish a connection with the provisioning server based on the broadcast network information. Once a connection is established, the provisioning client can communicate with the provisioning server in order to perform software provisioning.

Additionally, in embodiments, in order to locate a provisioning server, the provisioning client can be configured to maintain a record of available provisioning servers. The record can include the network information (network identity, network location, and configuration) for each available provisioning server and a priority value for each available provisioning server. The locater module can be configured to select one of the available provisioning servers from the record for establishing a connection. The locater module can select the provisioning server based on the priority value. Once selected, the provisioning client can be configured to establish a connection with the selected provisioning server. Additionally, if a connection cannot be established with the selected provisioning server or the connection is not optimal, the provisioning client can be configured to select a different provisioning server from the record.

By automatically locating the provisioning server, the provisioning client can facilitate software provisioning without interaction from a user or administrator to establish a connection to the server. As such, the provisioning client can be utilized by users that may not have detailed knowledge of the software provisioning environment. Additionally, because the provisioning server is automatically detected, the provisioning client can be universally used in wide geographic areas without modification to the provisioning client.

FIG. 1 illustrates an overall provisioning environment 100, in systems and methods for the execution, management, and monitoring of software provisioning, according to exemplary aspects of the present disclosure. Embodiments described herein can be implemented in or supported by the exemplary environment illustrated in FIG. 1. The provisioning environment 100 provides a unified provisioning environment, which comprehensively manages the tasks related to software provisioning.

In particular, the provisioning environment 100 can manage software provisioning using a hierarchy of commands. In exemplary embodiments, the hierarchy can include at least four levels of commands. The lowest level in the hierarchy can comprise distribution commands, which primarily handle base operating system specific tasks of provisioning. The second level can comprise profile commands, which associate a configuration file, such as a kickstart file for Linux or other operating system, with a distribution and optionally allow for customization. The third level comprises system commands, which associate remote systems that are involved with the provisioning of the software. The fourth level comprises repository commands, which address configurations and tasks related to updating the software, remote installation procedures, and optionally customizing the software.

The provisioning environment 100 provides several capabilities and advantages over the known provisioning solutions. For example, the present invention is capable of handling a variety of forms of installations, such as preboot execution environment (“PXE”), virtualization, re-installations, and image installations.

In exemplary aspects, the provisioning environment 100 enables integrating virtualization into a PXE provisioning infrastructure and provides several options to reinstall running machines as well. The provisioning environment 100 can integrate mirroring of package repositories with the provisioning process, so that a provisioning server may serve as a central mirror point of contract for all of an organization's software needs. In aspects, a set of remote mirrored repositories can automatically be used by provisioned systems without additional setup.

Reference will now be made in detail to the exemplary aspects the provisioning environment 100. The provisioning environment 100 can be applied to provisioning any form of software, such as Windows systems, UNIX systems, and Linux systems. In the exemplary description that follows, FIG. 1 is presented to explain the provisioning environment 100 for provisioning software, such as Linux, and Linux based software, such as Fedora and Red Hat Enterprise Linux by Red Hat, Inc.

In provisioning of software such as Linux, many system administrators use what is known as the “kickstart” installation method. Kickstart files are files that specify the intended configuration of the software being provisioned. Kickstart files can be kept on a server and can be read by individual computers during the installation. This installation method allows the use a single or relatively few standard kickstart files to install Linux on multiple machines, making it ideal for network and system administrators.

The kickstart file can be a simple text file, containing a list of items, each identified by a keyword. In general, a kickstart file can be edited with any text editor or word processor that can save files as ASCII text. One skilled in the art will recognize that the present invention may be applied to non-kickstart files in software provisioning. For example, configuration files such as AutoYAST Answer files used in Novell SuSe Linux and Sun Solaris Jumpstart files may also be used by the provisioning environment 100.

Typically, a kickstart file can be copied to the boot disk, or made available on the network. The network-based approach is most commonly used, as most kickstart installations for software provisioning, such as Linux systems, tend to be performed via a network using NFS, FTP, or HTTP on networked computers. Administrators also find it desirable that kickstart installations can be performed using a local CD-ROM, or a local hard drive.

Using kickstart files, a system administrator can create a single file containing the parameters that are needed to complete a typical software installation. For example, kickstart files specify parameters related to: language selection; mouse configuration; keyboard selection; boot loader installation; disk partitioning; network configuration; NIS, LDAP, Kerberos, Hesiod, and Samba authentication; firewall configuration; and package selection.

According to exemplary aspects illustrated in FIG. 1, the provisioning environment 100 can include a provisioning server 102, a code repository 104 which provides access to distributions 106 and 108, a set of installation templates 110, a set of exception plugins 112, a helper client 114 running on target machines 116 in a network 115, a provisioning database 120 which comprises a distribution tree list 122 and template list 124. Each of these components will now be further described.

The provisioning server (from herein referred to as a “cobbler”) 102 is responsible for: serving as a extensible markup language remote procedure call (XMLRPC) handler; linking to or mirroring install distribution trees and a configuration database; hosting kickstart templates; hosting plugins, generating installation images, and the like. The cobbler server 102 can be implemented as software, such as Python code, installed on a boot server machine and provides a command line interface for configuration of the boot server. In addition, the cobbler server 102 can make itself available as a Python application programming interface (API) for use by higher level management software (not shown). The cobbler server 102 supports provisioning via PXE, image (ISO) installation, virtualization, re-provisioning. As will be described later, the last two modes are performed with the assistance of a helper client 114.

The code repository 104 is responsible for hosting distributions 106 and 108. The code repository 104 may be implemented using well known components of hardware and software. Additionally, the code repository 104 can be include one or more repositories hosting distributions. The distributions 106 and 108 can include bundles of software that is already compiled and configured. The distributions 106 and 108 may be in the form of either rpm, deb, tgz, msi, exe formats, and the like. For example, as Linux distributions, the distributions 106 and 108 are bundles of software that comprise the Linux kernel, the non-kernel parts of the operating system, and assorted other software. The distributions 106 and 108 can take a variety of forms, from fully-featured desktop and server operating systems to minimal environments.

In exemplary aspects, the installation templates 110 are any data structure or processing element that can be combined with a set of installation configurations and processed to produce a resulting configuration file, such as a kickstart file.

In exemplary aspects, exception plugins 112 is software that interacts with cobbler server 102 to customize the provisioning of software. In general, the exceptions plugins 112 are intended to address infrequent customization needs.

In exemplary aspects, the helper client (known as “koan”, which stands for “kickstart-over-a-network”) 114 can assist the cobbler server 102 during the provisioning processes. The koan 114 can allow for both network provisioning of new virtualized guests and destructive provisioning of any existing system. When invoked, the koan 114 can request profile information from a remote boot server that has been configured with the cobbler server 102. In some aspects, what the koan 114 does with the profile data depends on whether it was invoked with --virt or -replace-self.

In exemplary aspects, the koan 114 can enable replacing running systems as well as installing virtualized profiles. The koan 114 can also be pushed out to systems automatically from the boot server. In some aspects, the koan client 114 is also written in Python code to accommodate a variety of operating systems, machine architectures, etc.

In exemplary aspects, the network 115 can include a number of the target machines 116. The target machines 116 can represent the particular machines to which software provisioning is directed. The target machines 116 may represent a wide variety of computing devices, such as personal computers, servers, laptop computers, personal mobile devices, and the like. In some aspects, the target machines 116 can represent distributed computing environments such as cloud computing environments. Although FIG. 1 shows several of the target machines 116, the provisioning environment 100 can be capable of managing a wide range environments, such as datacenters with thousands of machines or server pools with just a few machines. Additionally, the cobbler server 102 can be connected to multiple networks 115.

In exemplary aspects, the provisioning database 120 can serve as a data storage location for holding data used by the cobbler server 102. For example, as shown, the provisioning database 120 can comprise the distribution tree list 122 and the template list 124. The distribution tree list 122 can provide an inventory of the distributions 106 and 108 that are hosted or mirrored by the cobbler server 102. The template list 124 can provide an inventory of the templates 110 that are hosted by the cobbler server 102.

As noted above, the cobbler server 102 can manage provisioning using a hierarchical concept of distribution commands, profile commands, system commands, and repository commands. This framework enables the cobbler server 102 to abstract the differences between multiple provisioning types (installation, reinstallation, and virtualization) and allows installation of all three from a common platform. This hierarchy of commands also permits the cobbler server 102 to integrate software repositories 126 with the provisioning process, thus allowing systems to be configured as a mirror for software updates and third party content as well as distribution content.

Distributions can contain information about base operating system tasks, such as what kernel and initial ramdisk (“initrd”) are used in the provisioning, along with other information, such as required kernel parameters. Profiles associate one of the distributions 106 and 108 with a kickstart file and optionally customize it further, for example, using plugins 112. Systems commands associate a hostname, IP, or MAC with a distribution and optionally customize the profile further. Repositories contain update information, such as yum mirror information that the cobbler server 102 uses to mirror repository 104. The cobbler server 102 can also manage (generate) DHCP configuration files using the templates 110.

In exemplary aspects, the cobbler server 102 can use a provisioning environment that is fully templated, allowing for kickstarts and PXE files to be customized by the user. The cobbler server 102 uses the concept of “profiles” as an intermediate step between the operating system and the installed system. A profile is a description of what a system does rather than the software to be installed. For instance, a profile might describe a virtual web server with X amount of RAM, Y amounts of disk space, running a Linux distribution Z, and with an answer file W.

In exemplary aspects, the cobbler server 102 can provide a command line interface to configure a boot server in which it is installed. For example, the format of the cobbler server 102 commands can be generally in the format of: cobbler command [subcommand] [--arg1=] [--arg2=]. Thus, a user can specify various aspects of software provisioning via a single interface, such as a command line interface or other known interface. Examples of exemplary cobbler commands can be found in U.S. patent application Ser. No. 11/763,315, U.S. Patent Application Publication No. ______ and U.S patent application Ser. No. 11/763,333, U.S. Patent Publication No. ______, the disclosures of which are incorporated herein, in their entirety, by reference.

According to exemplary aspects, a user can use various commands of the provisioning environment 100 to specify distributions and install trees hosted by the code repository 104, such as a distribution from the distributions 106 or 108. A user can add or import a distribution or import it from installation media or an external network location.

According to exemplary aspects, in order to import a distribution, the cobbler server 102 can auto-add distributions and profiles from remote sources, whether this is an installation media (such as a DVD), an NFS path, or an rsync mirror. When importing a rsync mirror, the cobbler server 102 can try to detect the distribution type and automatically assign kickstarts. By default in some embodiments, the cobbler server can provision by erasing the hard drive, setting up eth0 for DHCP, and using a default password. If this is undesirable, an administrator may edit the kickstart files in /etc/cobbler to do something else or change the kickstart setting after the cobbler server 102 creates the profile.

According to exemplary aspects, a user may map profiles to the distributions and map systems to the profiles using profile commands and systems commands of the provisioning environment 100. A profile associates a distribution to additional specialized options, such as a kickstart automation file. In the cobbler server 102, profiles are the unit of provisioning and at least one profile exists for every distribution to be provisioned. A profile might represent, for instance, a web server or desktop configuration.

According to exemplary aspects, a user can map systems to profiles using system commands. Systems commands can assign a piece of hardware with cobbler server 102 to a profile. Systems can be defined by hostname, Internet Protocol (IP) address, or MAC address. When available, use of the MAC address to assign systems can be preferred.

According to exemplary aspects, the user can map repositories and profiles using repository commands. Repository commands can address configurations and tasks related to updating the software, remote installation procedures, and optionally customizing the software. These repository commands can also specify mirroring of the provisioned software to remote servers. Repository mirroring can allow the cobbler server 102 to mirror not only install the trees 106 and 108, but also optional packages, third party content, and updates. Mirroring can be useful for faster, more up-to-date installations and faster updates, or providing software on restricted networks. The cobbler server 102 can also include other administrative features, such as allowing the user to view their provisioning configuration or information tracking the status of a requested software installation.

According to exemplary aspects, a user can utilize commands to create a provisioning infrastructure from a distribution mirror. Then a default PXE configuration is created, so that by default systems will PXE boot into a fully automated install process for that distribution. The distribution mirror can be a network rsync mirror or a mounted DVD location.

According to exemplary aspects, the administrator uses a local kernel and initrd file (already downloaded), and shows how profiles would be created using two different kickstarts—one for a web server configuration and one for a database server Then, a machine can be assigned to each profile.

According to exemplary aspects, a repo mirror can be set up for two repositories, and create a profile that will auto install those repository configurations on provisioned systems using that profile.

According to exemplary aspects, in addition to normal provisioning, the cobbler server 102 can support yet another option, called “enchant”. Enchant takes a configuration that has already been defined and applies it to a remote system that might not have the remote helper program installed. Users might want to use this command to replace a server that is being repurposed, or when no PXE environment can be created. Thus, the enchant option allows the remote the koan client 114 to be executed remotely from the cobbler server 102.

According to aspects, if the cobbler server 102 is configured to mirror certain repositories, the cobbler server 102 can then be used to associate profiles with those repositories. Systems installed under those profiles can be auto configured to use these repository mirrors in commands and, if supported, these repositories can be leveraged. This can be useful for a large install base, fast installation and upgrades for systems are desired, or software not in a standard repository exists and provisioned systems are desired to know about that repository.

According to exemplary aspects, the cobbler server 102 may also keep track of the status of kickstarting machines. For example, the “cobbler status” will show when the cobbler server 102 thinks a machine started kickstarting and when it last requested a file. This can be a desirable way to track machines that may have gone inactive during kickstarts. The cobbler server 102 can also make a special request in the post section of the kickstart to signal when a machine is finished kickstarting.

According to exemplary aspects, for certain commands, the cobbler server 102 will create new virtualized guests on a machine in accordance to the orders from the cobbler server 102. Once finished, an administrator may use additional commands on the guest or other operations. The cobbler server 102 can automatically name domains based on their MAC addresses. For re-kickstarting, the cobbler server 102 can reprovision the system, deleting any current data and replacing it with the results of a network install.

According to exemplary aspects, the cobbler server 102 can configure boot methods for the provisioning requested by the user. For example, the cobbler server 102 can configure a PXE environment, such as a network card BIOS. Alternatively, the cobbler server 102 can compile and configure information for koan client 104. The cobbler server 102 can also optionally configured DHCP and DNS configuration information.

According to exemplary aspects, the cobbler server 102 can serve the request of the koan client 114. The koan client 114 can acknowledge the service of information of the cobbler server 102 and then can initiate installation of the software being provisioned. Additionally, the koan client 114 can either install the requested software, e.g., replace the existing operating system, or install a virtual machine.

FIG. 2 illustrates aspects of the provisioning environment 100 that allows for automatic location of provisioning servers in the provisioning environment 100, according to various embodiments. In embodiments as shown, a provisioning client 202, such as a koan client 114, can include a locater module 204. The locater module 204 can be configured to automatically locate a provisioning server, such as the cobbler server 102, in the provisioning environment 100 in order to perform software provisioning. The locater module 204 can locate the cobbler server 102 by detecting the location of the cobbler server 102 or by selecting the appropriate cobbler server 102 from a record of available provisioning servers. Once located, the provisioning client 202 can be configured to establish a connection with the cobbler server 102 and to request and receive software provisioning.

In embodiments, the locater module 204 can be implemented as a portion of the code for the provisioning client 202. Likewise, the locater module 204 can be implemented as a separate software tool accessible by the provisioning client 202. The locater module 204 can be written in a variety of programming languages, such as JAVA, C++, XML, Python code, and the like to accommodate a variety of operating systems, machine architectures, etc.

In embodiments, in order to locate the cobbler server 102, the provisioning client 202 can be configured to detect broadcast network information 206 from the cobbler server 102 in order establish a connection with the cobbler server 102. In particular, a cobbler server 102 can be configured to include a broadcast module 208. the broadcast module 208 can be configured to maintain or locate the network information 206 for the cobbler server 102 and to broadcast the network information 206 across the networks connected to the cobbler server 102. The network information 206 can include information such as network identification (host name, cobbler server name, etc.), network location (network address, etc.), or configuration (type of software provisioning supported, authentication information, etc.).

In embodiments, the broadcast module 208 can be implemented as hardware, software, and combinations thereof. Additionally, the broadcast module 208 can utilize any type of network protocol or procedure, such as zeroconf protocols, to broadcast the network information 206. For example, the broadcast module 208 can utilize multicast DNS, using such software or tools as Avahi and/or BONJOUR/RENDEVOUS by APPLE, Corp., to broadcast the network information 206.

In embodiments, in order establish a connection, the locater module 204 can be configured to automatically detect the broadcast network information 206 from the cobbler server 102. In particular, the locater module 204 can be configured to listen to the networks connect to the provisioning client 202 in order to detect any network information 206. The locater module 204 can utilize any type of network protocol or procedure, such as zeroconf protocols, to detect the network information 206. For example, the locater module 204 can utilize multicast DNS, using such software or tools as Avahi and/or BONJOUR/RENDEVOUS by APPLE, Corp.

Once detected, the provisioning client 202 can establish a connection with the cobbler server 102 based on the broadcast network information 206. In particular, the provisioning client 202 can utilize the network information 206 to configure the provisioning client 202 to communicate with cobbler server 102.

Additionally, in embodiments, the provisioning client 202 can be configured to provide authentication information 210 to the cobbler server 102. Authentication information 210 can include any type of data that can be created and verified using well-known security and cryptographic processes, such as such as digital certificates, digital signature, cryptographic authentication, and the like, in order to establish and verify the identity of the provisioning client 202. The cobbler server 102 can be configured to utilize any well-know security and cryptographic processes to authenticate and verify the authentication information 210. Additionally, the provisioning client 202 can be configured to authenticate the cobbler server 102 utilizing similar processes.

Additionally, in embodiments, in order to locate the cobbler server 102, the provisioning client 202 can be configured to maintain a record 212 of available provisioning servers, such as the cobbler server 102 and provisioning servers 214. Provisioning servers 214 can be configured as cobbler servers or any other type of software provisioning server. The provisioning client 202 can be configured to maintain the list in any type of format such as a network service record (DNS SRV records).

In embodiments, the record 212 can include the network information, such as such as network identification (host name, cobbler server name, etc.), network location (network address, etc.), or configuration (type of software provisioning supported, authentication information, etc.), for each available provisioning server and a priority value for each available provisioning server. The priority value can represent the order by which the provisioning client 202 will select the provisioning servers. The locater module 204 can be configured to select one of the available provisioning servers from the record 212 for establishing a connection. For example, the cobbler server 102 can have the highest priority value and the locater module 204 can select the cobbler server 102. Once selected, the provisioning client 202 can be configured to establish a connection with the cobbler server 102, as mentioned above.

Additionally, in embodiments, if a connection cannot be established with the selected provisioning server or the connection is not optimal, the provisioning client 202 can be configured to select a different provisioning server from the record 212. For example, if cobbler server 102 is not available or not optimal, the locater module 204 can be configured to select the next available provisioning server with the next highest priority value. The provisioning client 202 can be configured to determine if the provisioning server is optimal based on such parameters as network performance, provisioning server availability, provisioning services offered by the provisioning server, geographic location of the provisioning server, and the like.

Additionally, in embodiments, in order to locate the cobbler server 102, the provisioning client 202 can be configured to search for the provisioning servers by common identification. For example, the locater module 204 can search for common names of provisioning servers, such as “cobbler.”

Once a connection is established by any of the processes, the provisioning client 202 can communicate with the cobbler server 102 in order to perform software provisioning. The software provisioning can include any type of provisioning described above, such as software installs, software re-installs, virtualization, and the like. The software provisioning can be at the request of provisioning client 202 or at the direction of cobbler server 102.

Additionally, the provisioning client 202 can be configured to update the record 212 so that it accurately contains available provisioning servers. The provisioning client 202 can update the record 212 on demand or periodically. The provisioning client 202 can update the record 212 by utilizing locater module 204 to listen for broadcast network information from provisioning servers. Likewise, the provisioning client 202 can be configured to request updated network information for the available provisioning servers. For example, the provisioning client 202 can query each of the available provisioning servers to determine if each server is still available or if the network information has changed.

Additionally, in embodiments, the cobbler server 102 can be configured to assist in selecting a provisioning server for the provisioning client 202. In particular, the cobbler server 102 can be configured to maintain a record 216. Record 216 can include a list of available provisioning server, such as provisioning servers 214. The record 216 can also include information about each provisioning server such as the network information of the provisioning servers, software distribution services provided by each, the types of software provided by each. The cobbler server 102 can maintain record 216, for example, in the database 120.

In embodiments, if a different provisioning server is optimal for the provisioning client 202, the cobbler server 102 can provide the network information to the provisioning client 202 in order to establish a connection. The cobbler server 102 can determine the optimal provisioning server based on the network traffic of the provisioning servers, availability of the provisioning servers, geographic location of the provisioning server, software distribution services provided, the types of software provided, and the like. Additionally, the cobbler server 102 can periodically provide the information in record 216 to the provisioning client 202 so that provisioning client 202 can update record 212.

FIG. 3 illustrates an exemplary diagram of hardware and other resources that can be incorporated in the cobbler server 102 configured to communicate with the network 115 and the provisioning clients 202 in network 115, according to embodiments. In embodiments as shown, the cobbler server 102 can comprise a processor 300 communicating with memory 302, such as electronic random access memory, operating under control of or in conjunction with operating system 306. Operating system 306 can be, for example, a distribution of the Linux™ operating system, the Unix™ operating system, or other open-source or proprietary operating system or platform. Processor 300 also communicates with the provisioning database 120, such as a database stored on a local hard drive. While illustrated as a local database in the cobbler server 102, the provisioning database 120 can be separate from the cobbler server 102 and the cobbler server 102 can be configured to communicate with the remote provisioning database 120.

Processor 300 further communicates with network interface 304, such as an Ethernet or wireless data connection, which in turn communicates with one or more networks 115 and the provisioning client 202, such as the Internet or other public or private networks. Processor 300 also communicates with the provisioning database 120 and the broadcast module 208, to execute control logic and perform the software provisioning processes described above. Other configurations of the cobbler server 102, associated network connections, and other hardware and software resources are possible.

While FIG. 3 illustrates the cobbler server 102 as a standalone system comprising a combination of hardware and software, the cobbler server 102 can also be implemented as a software application or program capable of being executed by a convention computer platform. Likewise, the cobbler server 102 can also be implemented as a software module or program module capable of being incorporated in other software applications and programs. In either case, the cobbler server 102 can be implemented in any type of conventional proprietary or open-source computer language.

FIG. 4 illustrates a flow diagram of overall provisioning server detection processes in the provisioning environment 100, according to embodiments of the present teachings. In 402, the process can begin. In 404, the provisioning client 202 can be configured to automatically locate the provisioning server, such as the cobbler server 102, in the provisioning environment 100 in order to perform software provisioning. The provisioning client 202 can locate the cobbler server 102 by detecting the location of the cobbler server 102 or by selecting the appropriate cobbler server 102 from a record 212 of available provisioning servers.

Once located, in 406, the provisioning client 202 can be configured to establish a connection with the cobbler server 102 and to request or receive software provisioning. During establishing a connection, the provisioning client 202 can be authenticated by the cobbler server 102 and, likewise, the provisioning client 202 can authenticate the cobbler server 102.

Optionally, in 408, the cobbler server 102 can direct the provisioning client 202 to a different provisioning server better suited for the software provisioning. Also, optionally, in 410, the provisioning client 202 can update the record 212. In 412, the process can end, but the process can return to any point and repeat.

While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments without departing from the true spirit and scope. The terms and descriptions used herein are set forth by way of illustration only and are not meant as limitations. In particular, although the method has been described by examples, the steps of the method may be performed in a different order than illustrated or simultaneously. Those skilled in the art will recognize that these and other variations are possible within the spirit and scope as defined in the following claims and their equivalents. 

1. A method of provisioning software in a software provisioning environment, comprising: instantiating a provisioning client on a target machine; locating, by the provisioning client, a provisioning server in a network to assist the software provisioning; establishing a connection with the provisioning server; and receiving at least one software provisioning action based on at least one of a set of software distributions, a set of installation templates, or a set of installation profiles.
 2. The method of claim 1, wherein locating the provisioning server comprises: detecting network information broadcast in the network, the network information comprising at least one of a network location of the provisioning server, a network identity of provisioning server, or a configuration of the provisioning server; and establishing the connection based on the network information.
 3. The method of claim 1, wherein locating the provisioning server comprises: maintaining, in the provisioning client, a record of available provisioning servers, wherein the record comprises at least one of a network location of each available provisioning server, a network identity of each available provisioning server, a configuration of each available provisioning server, or a priority of each available provisioning server; selecting one of the available provisioning servers as the provisioning server; and establishing the connection with the selected one of the available provisioning servers.
 4. The method of claim 3, wherein selecting the one of the available provisioning servers comprises selecting based on the priority value of each provisioning server.
 5. The method of claim 3, further comprising: selecting a second of the available provisioning servers if the connection cannot be established with the selected one of the available provisioning servers.
 6. The method of claim 3, further comprising: updating the record.
 7. The method of claim 3, wherein the record is a domain name system (DNS) service record.
 8. The method of claim 1, wherein locating, by the provisioning client, the provisioning server comprises: searching for the provisioning server based on a common identification.
 9. The method of claim 1, where establishing the connection with the provisioning server comprises providing authentication information to the provisioning server.
 10. A provisioning client, the provisioning client being embodied in a computer readable medium and comprising instructions for causing a computer to perform a method comprising: locating a provisioning server in a network to assist with software provisioning; establishing a connection with the provisioning server; and receiving at least one software provisioning action based on at least one of a set of software distributions, a set of installation templates, or a set of installation profiles.
 11. The provisioning client of claim 10, wherein locating the provisioning server comprises: detecting network information broadcast in the network, the network information comprising at least one of a network location of the provisioning server, a network identity of provisioning server, or a configuration of the provisioning server; and establishing the connection based on the network information.
 12. The provisioning client of claim 10, wherein locating the provisioning server comprises: maintaining a record of available provisioning servers, wherein the record comprises at least one of a network location of each available provisioning server, a network identity of each available provisioning server, a configuration of each available provisioning server, or a priority of each available provisioning server; selecting one of the available provisioning servers as the provisioning server; and establishing the connection with the selected one of the available provisioning servers.
 13. The provisioning client of claim 12, wherein selecting the one of the available provisioning servers comprises selecting based on the priority value of each provisioning server.
 14. The provisioning client of claim 12, the method further comprising: selecting a second of the available provisioning servers if the connection cannot be established with the selected one of the available provisioning servers.
 15. The provisioning client of claim 12, the method further comprising: updating the record.
 16. The provisioning client of claim 10, where establishing the connection with the provisioning server comprises providing authentication information to the provisioning server.
 17. A method of provisioning software in a software provisioning environment, comprising: broadcasting network information for a provisioning server in a network, the network information comprising at least one of a network location of the provisioning server, a network identity of provisioning server, or a configuration of the provisioning server; receiving a request from a provisioning client to establish a connection to the provisioning server to assist with software provisioning; and providing at least one software provisioning action to the provisioning client based at least one of a set of software distributions, a set of installation templates, or a set of installation profiles.
 18. The method of claim 17, further comprising: authenticating the provisioning client prior to providing the at least one software provisioning action.
 19. The method of claim 17, further comprising: determining a second provisioning server to provide the at least one software provisioning action; and providing network information of the second provisioning server to the provisioning client.
 20. The method of claim 17, wherein the broadcast of the network information comprises a multicast domain name system (DNS) broadcast.
 21. A system for providing software provisioning in a software provisioning environment, comprising: a network interface to a network comprises at least one new system; and a provisioning server, communicating with the network interface, the provisioning server being configured to— broadcast network information for the provisioning server, the network information comprising at least one of a network location of the provisioning server, a network identity of provisioning server, or a configuration of the provisioning server; receive a request from a provisioning client to establish a connection to the provisioning server to assist with software provisioning; and provide at least one software provisioning action to the provisioning client based at least one of a set of software distributions, a set of installation templates, or a set of installation profiles.
 22. The system of claim 21, wherein the provisioning server is further comprising: authenticating the provisioning client prior to providing the at least one software provisioning action.
 23. The system of claim 21, wherein the provisioning server is further comprising: determining a second provisioning server to provide the at least one software provisioning action; and providing network information of the second provisioning server to the provisioning client.
 24. The system of claim 21, wherein the broadcast of the network information comprises a multicast domain name system (DNS) broadcast. 